Technical

business objects

There are some common properties, which all Atlas business objects posses – id, name, description and inserted, updated and deleted timestamp. These settings are encapsulated in the ABean abstract class. The id of the entity is a unique identifier, enclosed by an instance of the IProxy interface. This instance also contains flags, which show if the entity is new, changed or deleted. The diagram below depicts the structure of the business objects in Atlas:

adapter services

The adapter services are actually osgi services, which implement the IAtlasAdapterFactory interface. They are used to adapt one business object type to another. All such services provide two methods:

public Class< ? >[] getAdapterList() - provides a list of classes, to which the service can adapt.

public < C > C getAdapter( Object adaptable, Class< C > adapterType, Map< String, Object > pProperties )- checks if the adapter service can transform the adaptable argument to the adapter type.

The IAtlasAdapterManager service contains and manages the IAtlasAdapterFactory services. It accepts the business object to be adapted and the type, to which it should be transformed. Afterwards, the manager iterates through the adapter factories, which can adapt to the required type, in order to find one, which can transform the given business object.

The next sections list the components of the system, which are defined on a domain basis – content model, users and groups, data filters, selections, approval procedures and categorization trees.